Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1138

reference: 415-tree-1
name: 1138
tree-preservation-order: undefined
415-tpo-1
uprn
address-text
point: POINT (-1.015048 50.892253)
geometry: MULTIPOLYGON (((-1.015005 50.892249,-1.015007 50.892257,-1.015013 50.892265,-1.015023 50.892271,-1.015034 50.892275,-1.015048 50.892276,-1.015061 50.892275,-1.015073 50.892271,-1.015082 50.892265,-1.015089 50.892258,-1.015091 50.892250,-1.015089 50.892241,-1.015083 50.892234,-1.015074 50.892228,-1.015062 50.892224,-1.015049 50.892222,-1.015035 50.892223,-1.015024 50.892227,-1.015014 50.892233,-1.015008 50.892240,-1.015005 50.892249)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL